How to create and use the Requirement Traceability Matrix in Jira?

Originally published June 14, 2019, updated for accuracy April 29, 2024

Using the requirements traceability matrix in Jira for testing can be great for your team. The feature simplifies test tracking and workflow organization. It results in improved QA processes and a notable reduction in potential bugs. Discover how to set up the traceability matrix that matches your needs.

Traceability helps teams keep track of their project tasks and understand how they fit into the bigger picture. There are two main types of traceability: forward and backward. 

Both types ensure that teams stay aligned with project objectives.

When it comes to testing, checking coverage is crucial to releasing a bug-free product. In Jira, test coverage tells you how much of your software is tested. It shows if all the important parts are checked by your tests. High test coverage means more of your program is examined. Low test coverage means some parts might not be thoroughly tested and require attention.

Requirements traceability means connecting testing tasks to specific project requirements. This ensures that each activity aligns with the project’s goals. Traceability tools help your team double-check if the important aspects weren’t overlooked. 

The quote above is very much to the point. Traceability gives you multiple tracking possibilities. You can analyze the testing object relations and follow every phase step by step like GPS instructions. Thanks to this, your team can reach the project’s goal at the minimum cost and time and maximum quality.

Native Jira doesn’t have a traceability matrix for testing among its functionalities. The basic features of the Atlassian product often aren’t enough for advanced users. Especially when you aim for a consistent testing process. The majority of projects tend to require more complex solutions. Fortunately, there’s a wide range of dedicated test management plugins designed to make testers’ work more efficient. One of them is our Requirements and Test Management for Jira (RTM). 

Requirements and Test Management for Jira allows one to track the whole project from end to end. Gather requirements, assign test cases to them, set up test plans, and verify their executions. Report defects, and check coverage. You can do all that in a single place. Last but not least, the app lets you seamlessly link testing objects to Jira epics and user stories. You can also search for them like for regular Jira issues. Using RTM for Jira, you’ll get an embedded process inside the project management tool you and your team already know.

As mentioned before, Jira doesn’t provide a built-in requirements traceability matrix. This is why we will explain the configuration using an example of Requirements and Test Management for Jira plugin. 

The Traceability Matrix is a special panel that lists issues of one type and verifies their associations with requirements, tests, or defects. It also shows the total number of relationships for each issue and the percentage of coverage for both the X and Y axes (columns and rows of the chart).

To set up the matrix in RTM for Jira: 

The Traceability Matrix is perfect for tracking requirements and test case coverage. The feature allows you to choose among functional, non-functional, UI, and business requirements. It displays only the relations you’d like to see at the moment. With the matrix, linking requirements to test cases becomes clear for everyone. 

The Requirements Traceability Matrix presents a relationship comparison between two baselined issue types of our choice on a dedicated view. It can show you more than just associations between requirements and test cases. It also lets you:

Thanks to the report, you can see at a glance which tasks take more time than others or cause difficulties. Secondly, you can check if the test executions are complete as planned. Finally, you can look for defects and if there are any, track their source. Knowing from which testing object they result, simplifies fixing them without messing with other parts of the project.